<div id="Compatibility"></div>
<div class="header">
<p>
Next: [[cvs: Troubleshooting#Troubleshooting|Troubleshooting]], Previous: [[cvs: All environment variables which affect CVS#All environment variables which affect CVS|Environment variables]], Up: [[cvs#Top|Top]] &nbsp; |[[cvs: Index#SEC_Contents|Contents]]||[[cvs: Index#Index|Index]]|</p>
</div>

----

<div id="Compatibility-between-CVS-Versions"></div>
== Compatibility between CVS Versions ==

<div id="index-CVS_002c-versions-of"></div>
<div id="index-Versions_002c-of-CVS"></div>
<div id="index-Compatibility_002c-between-CVS-versions"></div>
The repository format is compatible going back to
<small>CVS</small> 1.3.  But see [[cvs: Using watches with old versions of CVS#Using watches with old versions of CVS|Watches Compatibility]], if
you have copies of <small>CVS</small> 1.6 or older and you want
to use the optional developer communication features.

The working directory format is compatible going back
to <small>CVS</small> 1.5.  It did change between <small>CVS</small> 1.3
and <small>CVS</small> 1.5.  If you run <small>CVS</small> 1.5 or newer on
a working directory checked out with <small>CVS</small> 1.3,
<small>CVS</small> will convert it, but to go back to <small>CVS</small>
1.3 you need to check out a new working directory with
<small>CVS</small> 1.3.

The remote protocol is interoperable going back to <small>CVS</small> 1.5, but no
further (1.5 was the first official release with the remote protocol,
but some older versions might still be floating around).  In many
cases you need to upgrade both the client and the server to take
advantage of new features and bugfixes, however.


This document was generated on <i>a sunny day</i> using [http://www.nongnu.org/texi2html/ <i>texi2html</i>].
